Repository navigation
WP1: the site on Workers - #2
Merged
Merged
Conversation
9d8's next-wp in apps/web: Next.js 16.3.8, Tailwind CSS 4 and shadcn/ui, built by next build (Turbopack), then @opennextjs/cloudflare (standalone output, the static-assets incremental cache) into one Worker with Static Assets. Every page that reads WordPress — /posts with search, filters and pagination, a post, /pages, a page, the category, tag and author lists, the sitemap — is force-dynamic and its fetches no-store, so it reads the REST API on every request; /api/og runs on the Node.js runtime; /api/revalidate is kept and secret-checked, with no cache to clear. WORDPRESS_URL is inlined at build from an optional Orun secret; with none the client answers from lib/sample.ts — three posts, a page, their terms and an author in the REST API's shapes and filters — under a 'no WordPress site is connected' notice, so a fresh site deploys and passes its smoke. Images are unoptimised; @vercel/analytics is the Cloudflare Web Analytics beacon. The site's name is one seam (SITE_NAME in site.config.ts, the root title included); site_domain is NEXT_PUBLIC_SITE_URL, set per environment by the deploy. tests/web: the template's own tests unchanged, the sample mode, the no-store fetches, the name and the origin. typecheck, lint, test and build are green; wrangler dev serves every route, unconnected, and the webhook answers 401 without its secret. Co-Authored-By: Claude <noreply@anthropic.com> Orun-Task: WP-2
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
9d8's next-wp in apps/web: Next.js 16.3.8, Tailwind CSS 4 and shadcn/ui, built by next build (Turbopack), then @opennextjs/cloudflare (standalone output, the static-assets incremental cache) into one Worker with Static Assets. Every page that reads WordPress — /posts with search, filters and pagination, a post, /pages, a page, the category, tag and author lists, the sitemap — is force-dynamic and its fetches no-store, so it reads the REST API on every request; /api/og runs on the Node.js runtime; /api/revalidate is kept and secret-checked, with no cache to clear. WORDPRESS_URL is inlined at build from an optional Orun secret; with none the client answers from lib/sample.ts — three posts, a page, their terms and an author in the REST API's shapes and filters — under a 'no WordPress site is connected' notice, so a fresh site deploys and passes its smoke. Images are unoptimised; @vercel/analytics is the Cloudflare Web Analytics beacon. The site's name is one seam (SITE_NAME in site.config.ts, the root title included); site_domain is NEXT_PUBLIC_SITE_URL, set per environment by the deploy. tests/web: the template's own tests unchanged, the sample mode, the no-store fetches, the name and the origin. typecheck, lint, test and build are green; wrangler dev serves every route, unconnected, and the webhook answers 401 without its secret.
🤖 Generated with Claude Code